\pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\f2\b0\i0\ul0\fs28 command line arguments argv argc parameters appkit\
\
Q: How can I use argv and argc?\
\
A: We do not recommend making your application rely on command line arguments because they will not be available when the program is launched by the Workspace Manager. Use the Defaults mechanism instead, and provide an Options or Preferences panel by which your users change the default values. See
\b NXRegisterDefaults
\b0 () and
\b NXGetDefaultValue
\b0 ().\
\
Currently the Application object sets various parameters based on command line argument pairs of the form "-
\i <flag>
\i0
\i <value>
\i0 " (such as -host MyHost or -NXShowPS YES ) and then removes those arguments from argv and argc. Your program should not depend on argv and argc, instead use the variables NXArgv and NXArgc that can be used anywhere within your program after the first message is sent, that is, after the initialize methods have completed. These variables will contain the arguments remaining after the Defaults-type arguments have been removed. NXArgv[0] will be the full pathname of a Workspace Manager-launched application. Note: if the program was launched from a shell then NXArgv[0] will contain the path specified in the command. In order to write a very robust app, one should check whether the value begins at "/". \
\
You will need to import <appkit/defaults.h> to get the declarations of the variables NXArgv and NXArgc.\
